1
00:00:00,240 --> 00:00:00,580
All right.

2
00:00:00,630 --> 00:00:08,070
Let's talk about insecurity serialization in this topic is kind of hard to wrap your mind around as

3
00:00:08,070 --> 00:00:12,240
to how it works because there's so many different ways that this could work.

4
00:00:12,240 --> 00:00:16,530
And unfortunately we're going to have to talk at a high level because there's not really a good application

5
00:00:16,530 --> 00:00:21,780
out there that we can utilize and we can't utilize our application for this attack.

6
00:00:21,810 --> 00:00:30,000
So this insecure D serialization we have to talk about what serialization is and what D serialization

7
00:00:30,000 --> 00:00:30,360
is.

8
00:00:30,390 --> 00:00:31,350
All right.

9
00:00:31,410 --> 00:00:42,660
So when we talk about serialization that is taking this data and we're going to convert an object into

10
00:00:42,690 --> 00:00:46,890
this format which can be put onto a disk right.

11
00:00:47,220 --> 00:00:54,810
And it can be sent over to a network or through a network so it can be serialized in a lot of different

12
00:00:54,810 --> 00:00:56,180
things.

13
00:00:56,250 --> 00:00:59,360
It could be serialized in Excel.

14
00:00:59,370 --> 00:01:10,020
Jason Gamble can be serialized in binary and it is you know it's serialized and it's sent over the opposite

15
00:01:10,020 --> 00:01:13,410
process of that is called D serialization.

16
00:01:13,980 --> 00:01:19,140
So that means we're taking this serialized data and then we're d serialized it.

17
00:01:19,140 --> 00:01:19,590
Right.

18
00:01:19,950 --> 00:01:22,470
So once we get it we we d serialize it.

19
00:01:22,950 --> 00:01:32,490
So the process of a insecure D serialization attack is when we have something malicious we take something

20
00:01:32,490 --> 00:01:40,830
malicious we have an exploit we serialize that exploit and then the application takes that data and

21
00:01:40,830 --> 00:01:43,870
it deals serialize is it and executes it.

22
00:01:43,890 --> 00:01:44,630
OK.

23
00:01:44,760 --> 00:01:46,860
And why does this happen why does this work.

24
00:01:46,860 --> 00:01:56,090
Well web apps are always using shouldn't they always they they use quite a bit serialization in D serialization

25
00:01:56,100 --> 00:01:56,840
right.

26
00:01:56,850 --> 00:01:58,770
So this is happening all the time.

27
00:01:58,770 --> 00:02:05,850
This is why this makes the top 10 is because we can utilize this kind of attack so we can send it something

28
00:02:05,850 --> 00:02:11,780
serialize and then it's going to take it and it's going to d serialize it and run it and execute it.

29
00:02:12,360 --> 00:02:21,810
Now these are kind of hard to find and there are so many different executable is out there and attacks

30
00:02:21,840 --> 00:02:29,310
and different programming languages that this goes to and software libraries et cetera that this makes

31
00:02:29,310 --> 00:02:36,540
it really really difficult to just go out there and find it but it doesn't mean that they're not out

32
00:02:36,540 --> 00:02:37,050
there.

33
00:02:37,110 --> 00:02:37,530
OK.

34
00:02:37,530 --> 00:02:41,070
So I definitely encourage you to read up on this.

35
00:02:41,070 --> 00:02:48,840
There's all kinds of cheap cheats on how to look for this and scan for this and really it comes down

36
00:02:48,900 --> 00:02:51,110
a lot to known vulnerabilities.

37
00:02:51,120 --> 00:02:54,620
And this is how to prevent it.

38
00:02:54,630 --> 00:03:00,600
It says here you know that you shouldn't accept serialized objects from untrusted sources.

39
00:03:00,600 --> 00:03:02,100
That's true.

40
00:03:02,100 --> 00:03:05,000
That's the best case scenario when we talk about prevention.

41
00:03:05,160 --> 00:03:10,770
If the source is untrusted you shouldn't accept anything right because then we're going to send it a

42
00:03:10,770 --> 00:03:11,860
serialized object.

43
00:03:11,880 --> 00:03:16,260
The application is going to take a d serialize it and it's going to execute that code.

44
00:03:17,010 --> 00:03:19,880
And we don't want that to happen as a developer.

45
00:03:20,510 --> 00:03:20,910
OK.

46
00:03:20,910 --> 00:03:23,340
So I encourage you again to read up on this.

47
00:03:23,340 --> 00:03:25,460
It is a complicated topic.

48
00:03:25,500 --> 00:03:27,150
It is by far not easy.

49
00:03:27,150 --> 00:03:33,200
And when you're talking about an interview process which is what we're after again here right.

50
00:03:33,360 --> 00:03:38,630
You should just know the serialization in D serialization process what it's using.

51
00:03:38,820 --> 00:03:43,790
And then there is a tool that you can read up on that people use quite a bit in it's called Why.

52
00:03:43,800 --> 00:03:51,450
So serial so read up on why so serial and what it does and how to kind of utilize it if you know that

53
00:03:51,450 --> 00:03:57,200
tool you know serialization is what civilization is and what these serialization is.

54
00:03:57,210 --> 00:03:59,680
I think you'll be fine in an interview.

55
00:03:59,880 --> 00:04:06,390
This one is kinda it's something you're not going to come across a lot but it still belongs in the top

56
00:04:06,390 --> 00:04:11,820
ten just for how you know how deadly I guess it can be.

57
00:04:11,820 --> 00:04:13,730
So that's it for this one.

58
00:04:13,800 --> 00:04:18,870
We're going to move on to number nine which is using components with known vulnerabilities and then

59
00:04:18,870 --> 00:04:24,210
we're going to talk about insufficient logging monitoring and in episode 10 or our topic 10 and then

60
00:04:24,210 --> 00:04:26,880
we're going to be done with the web app section.

61
00:04:26,880 --> 00:04:32,100
So I'll catch you over in the next video and we start talking about using components with known vulnerabilities.
